Skip to main content

This is a new service – your feedback will help us to improve it.

Newcastle City Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

North Gosforth, Brunton & Hazlerigg

reference
1997/001.W14
name
North Gosforth, Brunton & Hazlerigg
tree-preservation-order

undefined

1997/001
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-1.643924 55.034001,-1.643898 55.034128,-1.643865 55.034260,-1.643696 55.034900,-1.643549 55.035438,-1.643499 55.035641,-1.643327 55.036297,-1.643225 55.036674,-1.643138 55.037012,-1.643016 55.037516,-1.643012 55.037551,-1.643015 55.037591,-1.643039 55.037659,-1.643078 55.037788,-1.643118 55.037923,-1.643118 55.037937,-1.643153 55.037951,-1.643167 55.037935,-1.643181 55.037928,-1.643219 55.037892,-1.643275 55.037853,-1.643546 55.037634,-1.644102 55.037141,-1.643827 55.037029,-1.643291 55.037541,-1.643221 55.037508,-1.643224 55.037497,-1.643224 55.037477,-1.643242 55.037419,-1.643266 55.037330,-1.643617 55.035994,-1.643762 55.035437,-1.644047 55.034319,-1.644014 55.034166,-1.644022 55.034102,-1.644054 55.033894,-1.643975 55.033851,-1.643947 55.033838,-1.643537 55.033704,-1.643458 55.033682,-1.643065 55.033612,-1.642068 55.033429,-1.641796 55.033375,-1.641726 55.033359,-1.641687 55.033348,-1.641622 55.033323,-1.641411 55.033229,-1.640969 55.033024,-1.640828 55.033397,-1.642947 55.033799,-1.643361 55.033882,-1.643924 55.034001)))
point
POINT (-1.643028 55.035186)
notes
These data are update live via a feed to NCC's Tree Managament System, EzyTreev
entry-date
2022-07-01
start-date
1997-01-01
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Newcastle City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL